-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: update readline docs on EOL handling #4927
Conversation
@@ -118,7 +118,7 @@ the `input` stream receives a `^C`, respectively known as `SIGINT`. | |||
|
|||
`function (line) {}` | |||
|
|||
Emitted whenever the `input` stream receives a `\n`, usually received when the | |||
Emitted whenever the `input` stream receives `EOL`, usually received when the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be clearer if we explicitly said "end of line (\n
, \r
, or \r\n
)"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, will fix.
LGTM with a suggestion. |
8f2f779
to
537cb07
Compare
Fixed according to @cjihrig's suggestion. |
Thanks! Landed in 3218dfb. |
Added the lts-watch label. Doc updates like this should generally always be on the lts watch list unless they depend on a semver-minor or major. |
This commit explicitly calls out the end of line sequences used to generate line events in the readline module. Fixes: nodejs#4916 PR-URL: nodejs#4927 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
As raised in #4916 readline actually handles all the various forms of EOL (
\r
,\r\n
,\n
).